Multiple merchants in cardless payment transactions and multiple customers in cardless payment transactions

ABSTRACT

A method includes receiving a request for a list of nearby user devices, where the list of nearby user devices will be sent to a merchant device, where the merchant device is associated with a merchant, where the merchant operates a plurality of merchant devices, and where the merchant device is included in the plurality of merchant devices; receiving a respective location for one or more user devices, where each user device is associated with the merchant; determining, for each of the one or more user devices, whether the user device is nearby the merchant device, based on the respective location, to the merchant device than the other merchant devices in the plurality of merchant devices; generating the list of nearby user devices based at least on the determination; and sending the list of nearby user devices to the merchant device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/802,064, filed on Mar. 13, 2013, and entitled “Multiple Merchants inCardless Payment Transactions and Multiple Customers in Cardless PaymentTransactions,” which is a non-provisional of and claims priority to U.S.Provisional Patent Application No. 61/728,760, filed on Nov. 20, 2012,the entire contents of which are hereby incorporated by reference.

TECHNICAL FIELD

This disclosure relates to multiple merchants and multiple customers forcardless payment transactions.

BACKGROUND

In a conventional point-of-sale electronic credit card transaction, thetransaction is authorized and captured. In the authorization stage, aphysical credit card with a magnetic stripe is swiped through amerchant's magnetic card reader, e.g., as part of a point-of-saledevice. A payment request is sent electronically from the magnetic cardreader to a credit card processor. The credit card processor routes thepayment request to a card network, e.g., Visa or Mastercard, which inturn routes the payment request to the card issuer, e.g., a bank.Assuming the card issuer approves the transaction, the approval is thenrouted back to the merchant. In the capture stage, the approvedtransaction is again routed from the merchant to the credit cardprocessor, card network and card issuer, and the payment request caninclude the cardholder's signature (if appropriate). The capture statecan trigger the financial transaction between the card issuer and themerchant, and optionally creates a receipt. There can also be otherentities, e.g., the card acquirer, in the route of the transaction.Debit card transactions have a different routing, but also requireswiping of the card.

Many transactions require that the customer sign a physical receipt,electronically approve a transaction, e.g., by pressing an approvebutton on a user interface, electronically sign for the transaction,e.g., with a stylus or finger on an electronic signature capture devicewith a touch sensitive pad, or enter an authorizing personalidentification number (PIN).

Customers can conduct transactions with merchants that have multiplepoint-of-sales. The points-of-sale can be within one store location oracross multiple store locations.

SUMMARY

Merchants can have multiple points-of-sale provided by multiple merchantdevices. A system can provide information about nearby customers tonearby merchant devices and not other more distant merchant devices.Similarly, customers can search for multiple merchant devices. Ifmultiple devices are associated with a common merchant, the system canprovide a customer with the common merchant. The system determines theinformation provided to the merchants and customers based on locationsof user (e.g., customer) devices and merchant devices.

On the one hand, it would be generally convenient for a customer todispense with swiping of a credit card. On the other hand, the risk ofunauthorized transactions is a potential problem in a cardless paymenttransaction. An approach for conducting an electronic paymenttransaction without swiping a card is for the customer to provideauthorization that particular merchants can perform a cardless paymenttransaction, and for such transactions to only be authorized when thecustomer is within a predetermined distance of the merchant, e.g., assensed by the customer's mobile device.

In one aspect, a method includes receiving a request for a list ofnearby user devices, where the list of nearby user devices will be sentto a merchant device, where the merchant device is associated with amerchant, where the merchant operates a plurality of merchant devices,and where the merchant device is included in the plurality of merchantdevices; receiving a respective location for one or more user devices,where each user device is associated with the merchant; determining, foreach of the one or more user devices, whether the user device is nearbythe merchant device, where being nearby requires at least determiningthat the user device is geographically closer, based on the respectivelocation, to the merchant device than the other merchant devices in theplurality of merchant devices; generating the list of nearby userdevices based at least on the determination; and sending the list ofnearby user devices to the merchant device.

Implementations can include one or more of the following. The userdevice is associated with the merchant if the merchant has an indicationof consent of the user device to perform a payment transaction with themerchant. If the user device is nearby the merchant device, the list ofnearby user devices includes the user device. If the user device isgeographically closer to one of the other merchant devices than themerchant device, the list of nearby user devices does not include theuser device. If the user device is similarly distant, within a thresholdmargin, from the merchant device and from one of the other merchantdevices, the list of nearby user devices includes the user device.

In another aspect, a method includes receiving a request for a list ofnearby merchant devices, where the list of nearby merchant devices willbe sent to a user device; identifying a first plurality of merchantdevices around a location of the user device; identifying one or morepluralities of children merchant devices in the first plurality ofmerchant devices, where each merchant device in a plurality of childrenmerchant devices is associated with a common merchant, and where eachplurality of children merchant devices is associated with a uniquemerchant; determining, for each of the one or more pluralities ofchildren merchant devices, whether one or more merchant devices in theplurality of children merchant devices is within a radius around thelocation of the user device; generating the list of nearby merchantdevices based at on the determination; and sending the list of nearbymerchant devices to the user device.

Implementations can include one or more of the following. In thedetermining, for each of the one or more pluralities of childrenmerchant devices, if a merchant device in the one or more merchantdevices is outside the radius, the list of nearby devices includes themerchant device. If more than one merchant device in the secondplurality of merchant devices is within the radius, generating the listof nearby devices to include one of the merchant devices. The one of themerchant devices is the merchant device geographically closest to theuser device. The one of the merchant devices is a primary sales deviceof the merchant. The request includes the location of the user device.

Advantages may include one or more of the following. From a merchant'sperspective, a cardless payment system can provide information aboutnearby customers to nearby merchant devices and not other more distantmerchant devices. From a user's perspective, when searching for nearbymerchants, users can be provided with the identity of one merchant eventhough the merchant can have multiple merchant devices at the merchantlocation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of an example cardless payment systemarchitecture.

FIG. 2 is a diagram of an example implementation of the cardless paymentsystem.

FIG. 3 is a diagram of an example flow chart of the cardless paymentsystem.

FIG. 4 is a diagram of an example map illustrating multiple user devicesnear a merchant that has more than one merchant device.

FIG. 5 is a flow chart of an example method of providing nearbycustomers to a merchant device.

FIGS. 6A-B are diagrams of an example view of a merchant device'sapplication.

FIG. 7 is an example diagram of a customer device near multiple merchantdevices at one merchant location.

FIG. 8 is a flow chart of an example method of providing nearby merchantdevices to a customer.

FIG. 9 is a diagram of an example user interface on a customer device.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

As an overview, the system allows a user and a merchant to conductcardless payment transactions. Merchants can use multiple merchantdevices per merchant location. The system also allows a user (alsocalled a customer or payer) to purchase items from a merchant whilephysically present at the merchant, e.g., at any merchant point of sale,but using a cardless payment transaction. A cardless payment transactionis one where a user conducts the transaction with a merchant at a pointof sale using a financial account without physically presenting apayment card to the merchant at the point of sale. In fact, the merchantneed not receive any details about the financial account, e.g., thecredit card issuer, credit card number, and the like is not provided tothe merchant.

From the user's perspective, the user first signs up for an account withthe cardless payment system. The sign-up process requires certaininformation, such as information about a financial account sufficient toperform a transaction with the account. For example, if the financialaccount is a credit card account, then credit card information can beprovided, e.g., credit card number and expiration date. The user canalso sign up with other payment methods such as debit cards, pre-paidcards, bank accounts, or other third party financial accounts. The signup process can also require contact information for the user, e.g.,mailing address and email, and other personal identifying information,e.g., a photograph of the user. After creating an account, the user canselect a merchant that also has an account with the cardless paymentsystem. The user can give consent to perform a cardless paymenttransaction with the merchant if the user is within a predetermineddistance from the merchant. After the user gives consent, the merchantcan, without a presentment of the physical payment card, charge (in thecase of credit cards) or debit (in the case of debit cards) the user'sfinancial account for items the user wants to buy. Because the user'spayment card is already on file with the cardless payment system, theuser does not need to physically present a credit card to the merchant.

FIG. 1 is a schematic illustration of the architecture of an examplecardless payment system 100. The overall system 100 includes multipleuser devices 102, e.g., devices 102 a, 102 b, 102 c, and multiplemerchant devices 104, e.g., devices 104 a, 104 b, 104 c, connected to anetwork, e.g., the Internet 106. However, in some implementations, theoverall system 100 could have a single user device and multiple merchantdevices, or multiple user devices and a single merchant device. Eachuser device 102 a, 102 b, 102 c is a mobile computing device, i.e., ahand-held computing device, capable of running a user application. Forexample, the user device can be a smartphone or tablet computer. Eachmerchant device 104 a, 104 b, 104 c is also a computing device, capableof running a merchant application. The merchant device can be a mobiledevice, or it can be a desktop computer, a laptop computer, a dedicatedpoint of sale system, or other data processing apparatus.

A cardless payment processor operates a payment service system 108. Theuser and merchant devices can communicate with the payment servicesystem 108 using the network 106. The payment service system 108includes one or more servers 112, at least some of which can handlesecure transactions (e.g., a secure server), to processes alltransactions between the user devices 102 and merchant devices 104. Ingeneral, servers 112 can store public merchant information such as themerchant's address or phone number. The servers 112 can also beresponsible for transferring or updating the user application to theuser's mobile device or transferring or updating the merchantapplication to the merchant's computing device. In particular, theservers 112 can be responsible for sending information about merchantsthat have accounts with the cardless payment system to the user devices102. The servers 112 also handle secure information such as credit cardnumbers, debit card numbers, bank accounts, user accounts, useridentifying information or other sensitive information.

The payment service system 108 can communicate electronically with acard payment network 116, e.g., Visa, Mastercard, or the like. Thepayment service system 108 can communicate with a computer system 116 ofa card payment network, e.g., Visa or MasterCard. The payment servicesystem 108 can communicate with a computer system 116 over the samenetwork 106 used to communicate with the user devices 102, or over adifferent network. The computer system 116 of the card payment networkcan communicate in turn with a computer system 118 of a card issuer,e.g., a bank. There can also be computer systems of other entities,e.g., the card acquirer, between the payment service system 108 and thecard issuer.

Before a transaction between the user and the merchant can be performedusing the cardless payment system, the user must create a user accountwith the payment service system 108 and the merchant must create amerchant account with the payment service system 108.

The user can sign up using a mobile application or using an onlinewebsite, and can use a mobile device or another computing device, e.g.,a home computer. At some point prior to the transaction, a userapplication is downloaded to the user device, e.g., through anapplication store. Creation of the user account can be handled throughthe user application, or through another application, e.g., a genericweb browser. The user enters a name, account password, and contactinformation, e.g., email address. Before a transaction can be performed,the user also enters financial account information sufficient to conductthe transaction into the payment service system 108. For example, in thecase of a credit card account, the user can enter the credit cardissuer, credit card number and expiration date into the payment servicesystem 108; the card validation value and mailing address may also berequired. However, the financial account could also be associated with adebit card or pre-paid card, or another third party financial account.

In some implementations, the payment service system 108 requiresadditional personal identifying information before a transaction can beperformed. For example, the payment service system 108 may require aphoto of the user before a transaction can be performed. The photo ofthe user would be provided to the merchant so that the merchant cancompare the photo to the person. In addition, the payment service system108 can require a personal identification number (PIN) be entered by theuser. Other requirements can also be added to increase security. Thedata associated with a user account 114 can be stored at the servers112, e.g., in a database.

If the user is signing up with a mobile application, the user'sfinancial account information can be entered by swiping the financialtransaction card through a slot of a card reader coupled to the user'smobile device. Alternatively, the user can enter in financial accountinformation by typing in information at the mobile device, selecting acard from an application on the mobile device, from an online entity, orothers. In some implementations, another external application generatesa receipt that is sent to the user. The receipt then includes ahypertext link that allows a user to easily create a user account in thecardless payment system. For example, activating the link in the receiptcan automatically create a user account with a payment card prefilledwith the card used in the receipt to reduce effort by the user. Ineffect, activating a new account using a receipt auto-verifies the userinto the cardless payment system.

The merchant can sign up for an account using a merchant device, e.g.,104 a, 104 b, 104 c, or another device. The merchant enters a name,account password, and contact information, e.g., email address, andphysical location information, e.g., an address, into the paymentservice system 108. The merchant can also provide other information,e.g., a list of goods or services available, operating hours, phonenumber, a small identifying image logo or mark, to the payment servicesystem 108. The data associated with the merchant account 114 can bestored at the servers 112, e.g., in a database.

At some point prior to the transaction, a merchant application isdownloaded to the merchant device, e.g., through an application store.Creation of the merchant account can be handled through the merchantapplication, or through another application, e.g., a generic webbrowser.

Eventually, in order to receive funds from the transaction, the merchantwill need to enter financial account information into the paymentservice system sufficient to receive funds. For example, in the case ofa bank account, the user can enter the bank account number and routingnumber. However, the merchant's financial account can also be associatedwith a credit card account or another third party financial account. Inaddition, in some implementations, if the merchant has not entered thefinancial account information, the cardless payment processor can holdthe received funds until the financial account information is provided.

FIG. 2 is a diagram that outlines an example implementation of thecardless payment system 100. A user carries a mobile device 102 a withthe user application installed, and a merchant has a device 104 a withthe merchant application installed. Users and merchants each have anassociation, e.g., an account, with the payment service system 108.

Each merchant can be associated with multiple merchant devices. Themerchant can obtain device identifications for each merchant device andprovide the device identifications to the payment service system 108,e.g., saving the device identifications using the merchant application.The payment service system 108 can determine whether a merchant deviceis associated with the merchant based on the provided deviceidentification. Alternatively, each merchant device can run the merchantapplication, and the merchant can link the merchant device to themerchant using an interface of the merchant application.

The system can predetermine a geo-location distance 206, e.g., a radius,around the location of the merchant. In some implementations, thegeo-location distance 206 is 500 feet. In some implementations, thegeo-location distance 206 can be set by the merchant, e.g., the paymentservice system 108 receives input from the merchant device 104 oranother computer system of the merchant setting the location radius. Insome implementations, the payment service system 108 may limit theradius set by the merchant to a maximum location radius.

If the user device is located outside the geo-location radius 206 of themerchant, the merchant application does not provide an option to conducta cardless payment transaction with the user. In this case, the userdevice 102 a will indicate it is outside the geo-location radius 206 ofthe merchant, and the user device 102 can provide more information aboutthe merchant. However, the merchant device 104 a will be unable tocharge the user's financial account, as further described in referenceto FIG. 3.

If the user device 102 a is located within the geo-location radius 206of the merchant, the user can “check-in” with the merchant using anapplication on the user device 102 a as further described in referenceto FIG. 3 and FIG. 9. The user can configure the application toautomatically “check-in” with the merchant once the user is within thegeo-location radius 206 of the merchant, which will be further describedbelow in reference to FIG. 3. In some implementations, the user canconfigure the application to set a maximum amount that can be chargedper transaction with the merchant.

Checking in with a merchant allows the merchant application to displayan option to charge the user's financial account using a cardlesspayment transaction. In essence, checking in constitutes a consent bythe user to conduct a cardless transaction with the merchant. Thisconsent differs from actual authorization of the transaction, which theuser would provide, e.g., verbally, upon learning the amount of thetransaction.

In some implementations, in order to determine whether user device 102 ais within the geo-location radius 206 of the merchant device 104 a, themerchant's location, e.g., address, and the geo-location radius 206 forthe merchant are provided to the user device 102 a. The user device 102a can then use a geofencing function. For example, the user device 102 adetermines its own location, e.g., based on GPS information, cellphonedata, wireless network data, or the like, and then determines whetherits own location is within the geo-location radius 206 of the merchantlocation.

FIG. 3 is a diagram of an example flow chart of process conducted withthe cardless payment system 100. The process conducted with the cardlesspayment system 100 involves relationships between a user's mobiledevice, a server system, and a merchant's device. As described above,merchants can have multiple merchant devices. Some merchant devices canbe in proximity to each other, e.g., located within the same retailstore. These merchant devices can be associated with the same location,e.g., an address of the retail store, which is provided to the mobiledevice. Some merchant devices are not in proximity to each other, e.g.,merchant devices located at different store locations. These merchantdevices are associated with different locations. These differentlocations can be provided to the mobile device, and the mobile devicecan initiate cardless payment transactions with each different locationseparately even though the locations are associated with the samemerchant. The server system can reside in the payment service system 108and be configured to send and receive communications between the userdevice and the merchant device. The server system can include theservers 112. The communications can be encrypted using secure protocolsbuilt into the user device, server system, and merchant device. In someimplementations, this process is implemented through the applicationsinstalled on both the user's mobile device and the merchant's device.

In a typical situation, the user launches the user application on themobile device. The mobile device then displays a graphical userinterface (discussed further below with reference to FIG. 9). Inlaunching the user application, the mobile device 102 directs a requestto the server system to identify merchants that will perform cardlesspayment transactions. The request can be accompanied by locationinformation, e.g., as determined by the mobile device 102. The serversystem receives the request, and selects one or more merchants based onthe location information from the customer device and the storedlocation information for the one or more merchants. At least anidentification of the merchant and the location information for the oneor more merchants is sent to the mobile device 102. If a merchant hasmultiple store locations, each store location can be sent as anindividual entry in the list of merchants to the mobile device 102.Thus, the list of merchants can be displayed by the mobile devicewithout prior entry of the user of any other search terms or searchrestrictions.

The user may input a request for further information about a merchant,e.g., tap the name of the merchant in the list displayed by the userapplication, or press a “More Info” button on the user interface of theuser application. In response, the user device can display furtherinformation received regarding the merchant, e.g., the list of goods orservices available, operating hours, and phone number.

The user sends an indication of consent to perform a cardless paymenttransaction with the merchant to the server system. For example, theuser can request to “check in” with a merchant by interfacing with theuser application on the user device (step 302); this request canconstitute the indication of consent.

Alternatively, the request to identify a merchant, the display ofinformation concerning the merchant, and/or the indication of consent,could be entered into a computer other than the user device 102, e.g.,the user's home computer, that is logged in to the user's account on thepayment service system 108. In any event, should the user indicateconsent to perform the transaction, at least an identification of themerchant and the location information for the merchant is sent to themobile device 102.

The mobile device determines whether it is within the predetermineddistance from the merchant location (step 304). In some implementations,if the mobile device does not have the current location of the merchant,or if the merchant updated its location information for a set ofmerchant devices, the merchant location can be pushed or pulled into themobile device. Whether the mobile device is within the predetermineddistance can be determined, e.g., using a geolocation function providedby the operating system of the mobile device. Alternatively, if the useropts in to sharing of location information, the location information ofthe mobile device can be provided to the server of the payment servicesystem 108, and the server determines the distance between the merchantlocation and the mobile device.

As described above, if the mobile device determines the user's mobiledevice is not within a predetermined distance (e.g. 500 feet), themobile device displays a message indicating its inability to check in(e.g., a “too far to check in” message) and rejects the user's request(step 308). In this case, the mobile device can view information aboutthe merchant, but cannot check in. In other words, the merchant cannotcharge the user's financial account using a cardless payment transactionuntil the user is within the predetermined distance and the merchant hasthe user's consent.

On the other hand, if the mobile device is within the predetermineddistance, the mobile device sends an indication of proximity to theserver of the payment service system (step 306). In someimplementations, the user can automatically check in. For example, theuser first requests to automatically check in with a merchant at themerchant location. While this option is enabled, the mobile device canautomatically detect when it is within the predetermined distance andsend the indication of proximity. The indication of proximity can bedetermined using wireless network geo-fencing or GPS signals. In someimplementations, if the mobile device is not within the predetermineddistance, the user application will not permit the indication of consentto be provided. In some implementations, if the mobile device is notwithin the predetermined distance when an indication of consent isprovided, the user application will require that the user again providean indication of consent when the mobile device is within thepredetermined distance.

After the server receives this indication of proximity, the serversystem sends the indication of the mobile device's presence and personalidentifying information to the appropriate merchant device, e.g., amerchant device at the merchant location selected by the user (step310). In some implementations, personal identifying information includesthe user's name and picture. Upon receipt of this information, themerchant device displays the user's identifying information (step 314)on the graphical user interface (GUI) of the merchant application. Insome implementations, through the GUI of the merchant application, themerchant can select items that the user has sought to purchase. Theapplication can be configured to associate individual prices with eachof the merchant's items, and the application can automatically sum thetotal transaction amount that the user owes. In some implementations,the merchant can enter into the application a total sum of prices forall the items the user wishes to purchase, as well as tax or tip. A usercan authorize payment for a transaction by verbally notifying themerchant. For example, a user named John Smith can tell the merchant,“Put this on John Smith.” Before or after the user authorizes paymentfor the transaction, the merchant verifies the user's identity (step316). In some implementations, the merchant ensures the image displayedon the merchant device matches the user who is present in person.Assuming that the image matches, the merchant selects the transactionusing the GUI of the merchant application. In some implementations, themerchant can ask the user for more identifying information beforeprocessing the transaction such as the user's birthday, address, orother personal identifying information. After verifying the user'sidentity, the merchant interfaces with the merchant application to startprocessing the transaction.

In some implementations, the amount to be charged exceeds apredetermined amount set by the user, the merchant or the cardlesspayment processor. In this case, the user enters in a PIN associatedwith the user's account into the merchant device. The merchant deviceverifies the PIN with the server. Alternatively, the server system maycommunicate with the user device and cause the user device to requestthat the user enter the PIN into the user device. In yet anotheralternative, the server system can ask the user to confirm the paymenton the user device, removing the need to enter a PIN.

The merchant's device sends a record of the requested transaction to theserver (step 318). The server system continues processing the requestedtransaction (step 320) by sending the record to the computer system ofthe card payment network 116, e.g., Visa or MasterCard, and the cardpayment network 116 then sends the record to the card issuer, e.g., thebank, as described above.

If the transaction fails because it would exceed the credit limit orthere are insufficient funds in the financial account, the servernotifies the merchant application. In some implementations, the servercan notify both the merchant application and user application.

If the transaction succeeds and the server system receives approval fromthe card payment network 116, the server system communicates this to themerchant device. The merchant device then captures the transaction. Inthe capture stage, the approved transaction is again routed from themerchant to the credit card processor, card network and card issuer. Therecord of the transaction in the capture stage can the cardholder'ssignature (if appropriate), or other information. The capture state cantrigger the financial transaction between the card issuer and themerchant. On receipt of an indication from the card network that thetransaction has been captured, the server system optionally createsreceipts to send to the user, e.g., through the user application and/orthrough the previously provided contact email, and to the merchant (step322). Both devices then display the receipt in each of theirapplications (steps 324, 326). Optionally, the user may be permitted toopt out of notification.

FIG. 4 is a diagram of an example map 402 illustrating a cardlesspayment system that identifies multiple user devices near a merchantthat has more than one merchant device. The user devices and merchantdevices can be associated with a cardless payment system (e.g., thedevices have an account with the cardless payment system). A merchantcan have multiple merchant devices for multiple points of sale. MerchantDevice 1 404 is located at a different merchant location than MerchantDevice 2 406. Users A, B, and C can be carrying User devices A 408, B410, and C 412, respectively. User devices A, B, and C 408-412 arelocated at different places on the map 402. The cardless payment systemcan provide a list of nearby user devices to merchant devices, as willbe described below in reference to FIG. 5. Merchant devices can use thelist of nearby devices to assist in completing a cardless paymenttransaction, e.g., the list can provide identifying information of auser of a nearby device to a merchant.

FIG. 5 is a flow chart of an example method 500 of providing nearbyusers to a merchant device. More than one merchant device can beassociated with a common merchant. Each merchant device associated withthe common merchant can be provided with various sets of nearby users.Merchant devices can request a list of nearby user devices from thecardless payment system (e.g., using a merchant application). Merchantdevices can send this request periodically by polling the cardlesspayment system, or the cardless payment system can push updates ofnearby user devices to the merchant device.

The cardless payment system can receive the request from a merchantdevice (step 502). Each merchant device is associated with a merchant(e.g., a point of sale machine at a merchant location). The system canreceive locations from nearby user devices (step 504). For example, bothuser and merchant devices can provide their location to the cardlesspayment system upon startup of a customer/merchant application orperiodically as a background process. In some implementations, the userdevice provides its location to the cardless payment system whenever theuser device is authorized to perform a cardless payment transaction,e.g., is “checked in”, with the merchant at a merchant location asdescribed above in reference to FIG. 3. The system can store locationswhen provided by user and merchant devices. For example, in reference toFIG. 4, if Merchant Device 1 404 requests for a list of nearby userdevices, the cardless payment system receives the request. The systemcan receive locations of the nearby user devices. The system canidentify one or more user devices that have authorized cardless paymenttransactions with the merchant (e.g., User Devices A, B, and C 408, 410,and 412 are “checked in” with the merchant).

For a given user device, the system determines which merchant device isgeographically closer to the user device compared to other merchantdevices (step 506). For example, if locations are represented aslongitudes and latitudes, the system can calculate a distance betweeneach user device location and each merchant device location based on thelongitudes and latitudes. The system can use the distance to determineproximity between each user device and each merchant device.

The system then generates the list of nearby user devices based at leaston the determination (step 508). The list of nearby devices can includeidentifying information for each user of each nearby device. For a givenmerchant device, the list of nearby user devices includes user devicesthat are closer to the merchant device than other merchant devices.Also, for a given merchant device, the list of nearby user devices doesnot include user devices that are closer to other merchant devices thanthe given merchant device. The list of nearby devices can be provided tothe given merchant device. The merchant device can display identifyinginformation, e.g., a name and/or picture, of the user of the nearbydevice when running a merchant application.

In review, the system receives an indication that a user with anassociated user device is willing to perform a cardless transaction witha merchant. The system identifies the merchant device out of a pluralityof merchant devices of the merchant that is closest to the user device.Then the system checks in that particular user at the closest merchantdevice of the merchant; this merchant device (and not the more distantmerchant devices) is the one displayed in any list of merchants on theuser device, and this merchant device (and not the more distant merchantdevices) is the one that displays the presence of the user.

For example, in reference to FIG. 4, User Device A 408 is closer toMerchant Device 1 404 than Merchant Device 2 406. Therefore, thegenerated list of nearby user devices for Merchant Device 1 404 includesUser Device A. User Device C 410 is closer to Merchant Device 2 thanMerchant Device 1. Therefore, the generated list of nearby user devicesfor Merchant Device 2 includes User Device C 410.

In some implementations, the system determines a user device issimilarly distant from multiple merchant devices. For example, UserDevice B 412 can be similarly distant from Merchant Device 1 404 andfrom Merchant Device 2 406 within a threshold margin of distance (e.g.,0.2 mile, 0.5 mile, 1 mile, 5 miles, or more). In this case, the systemcan provide User Device B 412 to both Merchant Device 1 404 and MerchantDevice 2 406. Therefore, the generated list of nearby user devices forMerchant Device 1 404 includes User Devices A 408 and B 412. Also, thegenerated list of nearby user devices for Merchant Device 2 includesUser Devices B 412 and C 410. The system can send the generated list ofnearby user devices to the merchant device (step 510).

FIGS. 6A-B are diagrams of an example view of a merchant device'sapplication 602. If a user is associated with the cardless paymentsystem (e.g., “checked-in” with the merchant), the device can displaythe user's identifying information in the application. In someimplementations, the identifying information includes the user's name610, picture 608, phone number, email address, or other personalidentifying information. In some implementations, after verifying theuser's identity using the identifying information, the merchant entersin an amount 606 into the application using the keypad 604, shows theuser the amount to be charged, and taps an “Ok” button to cause thedevice to process the transaction.

FIG. 6A is a merchant application running on Merchant Device 1 404 inreference to FIG. 4. Merchant Device 1 404 can request for a list ofnearby user devices. As described above, User Devices A and B 408, 412are determined to be nearby Merchant Device 1 404. Merchant Device 1 404receives the generated list of nearby user devices including UserDevices A and B 408, 412. Therefore, the merchant application candisplay users A and B on the merchant device. The merchant applicationwill not display user C because User Device C is located closer toanother merchant device (e.g., Merchant Device 2 406) of the merchant.

FIG. 6B is a merchant application running on Merchant Device 2 406 inreference to FIG. 4. Merchant Device 2 406 can request for a list ofnearby user devices. As described above, User Devices B and C 410, 412are determined to be nearby Merchant Device 2 406. Merchant Device 2 406receives the generated list of nearby user devices including UserDevices B and C 410, 412. Therefore, the merchant application candisplay users B and C on the merchant device. The merchant applicationwill not display user A because User Device A is located closer toanother merchant device (e.g., Merchant Device 1 404) of the merchant.

FIG. 7 is an example map 702 of a cardless payment system thatidentifies a user device 708 near multiple merchant devices. The userdevices and merchant devices can be associated with a cardless paymentsystem (e.g., the devices have an account with the cardless paymentsystem). The system can detect a radius (e.g., radius r) around a userdevice's location. Merchant devices can be located at various merchantlocations. For example, the merchant Sightglass Coffee has threemerchant devices. Two of them, Sightglass Coffee Device 1 704 andSightglass Coffee Device 2 706, are located at one merchant location andare within a radius of the user device's location. Sightglass CoffeeDevice 3 710 is located at another merchant location. The system canalso identify merchants that have one merchant device (e.g., Casey'sPizza Device 1 712). The cardless payment system can provide a list ofnearby merchant devices to user devices, as will be described below inreference to FIG. 8.

FIG. 8 is a flow chart of an example method 800 of providing nearbymerchant devices to a user device. User devices can request a list ofnearby merchant devices from the cardless payment system (e.g., using auser application).

The cardless payment system can receive the request from a user devicefor a list of nearby merchant devices (step 802). In someimplementations, the request includes a location of the user device. Thesystem can identify a plurality of merchant devices around the locationof the user device (step 804). For example, the system can query amerchant database for the information based on the location. Themerchant database can include information of one or more childrenmerchant devices that are associated with the merchant. Childrenmerchant devices are merchant devices that are associated with a commonmerchant. For example, in reference to FIG. 7, “Sightglass Coffee” is acommon merchant that has three children merchant devices 704, 706, 710.

The system identifies one or more pluralities of children merchantdevices (e.g., from a merchant database) (step 806). Each plurality ofchildren merchant devices can be associated with a unique merchant. Forexample, in reference to FIG. 7, one plurality of children merchantdevices is associated with the merchant “Sightglass Coffee.”

The system determines, for each of the one or more pluralities ofchildren merchant devices, whether one or more merchant devices in theplurality of children merchant devices is within a radius around thelocation of the user device (step 808). For example, in reference toFIG. 7, the one or more merchant devices within a radius around thelocation of the user device includes Sightglass Coffee Device 1 704 andSightglass Coffee Device 2 706. Sightglass Coffee Device 3 710 is notwithin the one or more merchant devices because Sightglass Coffee Device3 710 is outside of the radius around the location of the user device.

The system can generate the list of nearby merchant devices based on thedetermination (step 810). Even if there are multiple children merchantdevices in the radius, the list of nearby merchant devices includes onemerchant listing that represents both merchant devices. For example, inreference to FIG. 7, Sightglass Coffee has two merchant devices withinthe radius. The generated list of nearby merchant devices will selectone of the two merchant devices (e.g., either Sightglass Coffee Device 1704 or Sightglass Coffee Device 2 706). If there were 10 or 20Sightglass Coffee Devices within the radius, the generated list ofnearby merchant devices will include only one of the merchant devices.In some implementations, the system selects the merchant device closestto the user device. In some other implementations, the system selectsthe merchant device that is a primary point of sale for the merchantlocation. The generated list also includes children merchant devicesthat are outside the radius (e.g., Sightclass Coffee Device 3 710 andCasey's Pizza Device 1 712). An example of the list of nearby merchantsis described below in reference to FIG. 9. The system can send thegenerated list of nearby merchant devices to the user device (e.g.,using the Internet) (step 812).

FIG. 9 is a diagram of example view of a user application's main page ona user's mobile device. The user application can retrieve a list ofmerchants 912 in response to an application query (e.g., on startup ofthe application). The application can display the list of merchants 912.

As mentioned above, in reference to FIG. 7, Sightglass Coffee has threemerchant devices, but the cardless payment system provides a list ofnearby merchants that includes two merchant listings to the user device.For example, the “Sightglass Coffee” listing that is 3 miles awayrepresents Sightglass Coffee Device 3 710. The “Sightglass Coffee”listing that is 1 mile away represents either Sightglass Coffee Device 1or 2 704, 706.

The list of merchants can be organized into a plurality of rows, eachrow containing the name 912 a of a single merchant. The list can alsoinclude an icon 912 b for each merchant, e.g., located in the row withthe name of the merchant. For example, each merchant's icon 912 b can belocated on the left side of the name 912 a of the merchant. In someimplementations, a cover image 908 for a merchant, e.g., the firstmerchant in the list, is displayed. The application can display adistance 910 that a merchant is from a current location of the mobiledevice. Again, the distance 910 can be located in the row with the name912 a of the merchant, e.g., on the right side of the name 912 of themerchant.

Each merchant can be represented with a custom-designed “card”. In someimplementations, tapping the row containing the name 912 a of themerchant, or tapping the name 912 a of the merchant, will cause theuser's mobile device to display more information regarding therespective merchant. In some implementations, the additional merchantinformation is represented by a custom-designed merchant page. Forexample, the mobile device can display a map around the merchant's area,the merchant's phone number, the merchant's operating hours, or othermerchant information.

The application can present user account information by tapping anaccount button 902. When provided with input, the application can searchfor merchants in a search bar 904. For example, the application can sendthe search query to a cardless payment system and be provided withmerchants that are relevant to the search query. Tapping a ‘favorites’button 906 can cause the application to retrieve a list of favoritesfrom the cardless payment system and display a list of favoritemerchants selected by the user.

To select a favorite, a user can perform a side swipe motion on amerchant listing. This can cause the application to bring up a list ofoptions related to the merchant. For example, the application candisplay options to favorite the merchant or share the merchant usingdifferent communication protocols (e.g., email or social networksharing). If a user selects a merchant as a favorite, the applicationsends the user's selection to the cardless payment system and associatesthe selection with the user's account.

If the current location of the mobile device is within a predetermineddistance of a merchant, the application can display a representativesymbol (e.g., “Check-in” button 914). By tapping the check in button,the application can perform the check in step described above inreference to FIG. 3. If the mobile device's current location is notwithin the predetermined distance, the application can display adistance 910 from the mobile device to the merchant. The applicationalso allows the user to “Explore Places” 916. In some implementations,this opens a list of nearby or featured merchants that are associatedwith the cardless payment system. A user then has an option to learnmore about one of the merchants in the list.

Embodiments of the subject matter and the operations described in thisspecification can be implemented in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Embodiments of the subject matterdescribed in this specification can be implemented as one or morecomputer programs, i.e., one or more modules of computer programinstructions, encoded on a non-transitory computer storage medium forexecution by, or to control the operation of, data processing apparatus.Alternatively or in addition, the program instructions can be encoded onan artificially-generated propagated signal, e.g., a machine-generatedelectrical, optical, or electromagnetic signal, that is generated toencode information for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can be a source or destination of computer programinstructions encoded in an artificially-generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate physical components or media (e.g., multiple CDs, disks, orother storage devices).

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing The apparatus can includespecial purpose logic circuitry, e.g., an FPGA (field programmable gatearray) or an ASIC (application-specific integrated circuit). Theapparatus can also include, in addition to hardware, code that createsan execution environment for the computer program in question, e.g.,code that constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languageresource), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub-programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto-optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), to name just a few.Devices suitable for storing computer program instructions and datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD (liquidcrystal display) monitor, for displaying information to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending resources to and receiving resources from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back-end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the subjectmatter described in this specification, or any combination of one ormore such back-end, middleware, or front-end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network (“LAN”) and a widearea network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

A system of one or more computers can be configured to performparticular operations or actions by virtue of having software, firmware,hardware, or a combination of them installed on the system that inoperation causes or cause the system to perform the actions. One or morecomputer programs can be configured to perform particular operations oractions by virtue of including instructions that, when executed by dataprocessing apparatus, cause the apparatus to perform the actions.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

What is claimed is:
 1. A method comprising: receiving, at one or morecomputing devices of a payment processor, and from a first user deviceassociated with a first user account, a selection of a merchant, from aplurality of merchants, the selection being indicative of consent toperform a cardless payment transaction with the merchant using a firstmerchant device associated with the merchant; storing, based on theselection and in a database of the one or more computing devices of thepayment processor, an indication of the consent in association with thefirst user account, the database further including a second user accountassociated with a second user device; receiving, from the first userdevice, a first current geolocation of the first user device; receiving,from the second user device, a second current geolocation of the seconduser device; determining, by the one or more computing devices of thepayment processor, that the first current geolocation of the first userdevice and the second current geolocation of the second user device areboth within a first geofence of the first merchant device associatedwith the merchant; generating, by the one or more computing devices ofthe payment processor, a first list of nearby user devices, the firstlist of nearby user devices including, from among the first user deviceand the second user device, the first user device based at least in parton determining that the first user device is within the first geofenceand the indication of consent stored in association with the first useraccount; and sending, by the one or more computing devices of thepayment processor, the first list of nearby user devices to the firstmerchant device.
 2. The method of claim 1, further comprising:receiving, from the first merchant device associated with the merchant,a request for an identification of nearby user devices, whereingenerating the first list of nearby user devices occurs at least partlyin response to the receiving the request for the identification ofnearby user devices.
 3. The method of claim 1, further comprising:determining that the first current geolocation of the first user deviceis within a second geofence of a second merchant device associated withthe merchant; generating a second list of nearby user devices, thesecond list of nearby user devices including the first user device; andsending the second list of nearby user devices to the second merchantdevice.
 4. The method of claim 3, further comprising: receiving, from atleast one merchant device associated with the merchant, a request for anindication of nearby user devices, wherein generating the first list ofnearby user devices and the generating the second list of nearby userdevices occur at least partly in response to receiving the request forthe indication of nearby user devices.
 5. A system comprising: aprocessor; and one or more computer-readable media coupled to theprocessor and having instructions stored thereon, which, when executedby the processor, cause the processor to perform operations comprising:receiving, from a user device, a selection of a merchant, from aplurality of merchants, the selection being indicative of consent toperform a cardless payment transaction with the merchant using a firstmerchant device associated with the merchant; receiving a currentgeolocation of the user device; determining that the current geolocationof the user device is within at least a first geofence of the firstmerchant device associated with the merchant; determining that at leastone other user device is also within the first geofence of the firstmerchant device from which no indication of consent to perform cardlesspayment transactions with the merchant is received; generating at leasta first list of nearby user devices corresponding to the first merchantdevice, the first list of nearby user devices including the user devicebased at least in part on determining that the current geolocation ofthe user device is within the first geofence of the first merchantdevice and receiving the selection from the user device that isindicative of the consent to perform the cardless payment transactionwith the merchant; and sending at least the first list of nearby userdevices to the first merchant device.
 6. The system of claim 5, theoperations further comprising: receiving, from at least the firstmerchant device associated with the merchant, a request for anindication of nearby user devices, wherein generating the at least thefirst list of nearby user devices occurs at least partly in response toreceiving the request for the indication of nearby user devices.
 7. Thesystem of claim 6, wherein the system processes payments for multiplemerchants including the merchant.
 8. The system of claim 6, theoperations further comprising: determining that the current geolocationof the user device is within a second geofence of a second merchantdevice associated with the merchant; generating a second list of nearbyuser devices, the second list of nearby user devices including the userdevice; and sending the second list of nearby user devices to the secondmerchant device.
 9. The system of claim 5, wherein the user device is amobile device that includes a global positioning system (GPS) receiver.10. The system of claim 5, wherein the user device is a mobile device,and the current geolocation of the user device is determined based atleast in part on one or more of cellphone data or wireless network data.11. The system of claim 5, wherein the receiving the current geolocationof the user device occurs after receiving the indication of consent toperform the cardless payment transaction with the merchant.
 12. One ormore non-transitory computer-readable storage media having instructionsstored thereon, which, when executed by a processor, cause the processorto perform operations comprising: receiving, from a first user device, aselection of a merchant, from a plurality of merchants, the selectionbeing indicative of consent to perform cardless payment transactionswith the merchant using a first merchant device; receiving a firstgeolocation of the first user device; determining that the firstgeolocation of the first user device is within a first geofence of thefirst merchant device associated with the merchant; determining that anumber of additional user devices are also within the first geofence ofthe first merchant device, the number of additional user devicesincluding at least one second user device from which a correspondingselection indicative of consent to perform cardless payment transactionswith the merchant using the at least one second user device has not beenreceived; generating a first list of nearby user devices, the first listof nearby user devices including the first user device based at least inpart on determining that the first user device is within the firstgeofence and receiving the selection of the merchant from the first userdevice to perform the cardless payment transactions, the first listexcluding the at least one second user device from which nocorresponding selection indicative of consent to perform cardlesspayment transactions with the merchant has been received; and sendingthe first list of nearby user devices to the first merchant device. 13.The one or more non-transitory computer-readable storage media of claim12, the operations further comprising: receiving, from the firstmerchant device associated with the merchant, a request for anidentification of nearby user devices, wherein generating the first listof nearby user devices occurs at least partly in response to receivingthe request for the identification of nearby user devices.
 14. The oneor more non-transitory computer-readable storage media of claim 12, theoperations further comprising: determining that a second geolocation ofa third user device is within the first geofence of the first merchantdevice associated with the merchant, the third user device havingprovided a corresponding selection of the merchant to indicate consentfor performing cardless payment transactions with the merchant using thethird user device, wherein the first list of nearby user devices furtherincludes the third user device based at least in part on determiningthat the second geolocation of the second user device is within thefirst geofence of the first merchant device and the correspondingselection of the merchant received from the third user device.
 15. Theone or more non-transitory computer-readable storage media of claim 12,the operations further comprising: determining that the firstgeolocation of the first user device is within a second geofence of asecond merchant device associated with the merchant; generating a secondlist of nearby user devices, the second list of nearby user devicesincluding the first user device; and sending the second list of nearbyuser devices to the second merchant device.
 16. The one or morenon-transitory computer-readable storage media of claim 15, theoperations further comprising: receiving, from at least one merchantdevice associated with the merchant, a request for an indication ofnearby user devices, wherein generating the first list of nearby userdevices and generating the second list of nearby user devices occur atleast partly in response to receiving the request for the indication ofnearby user devices.
 17. The one or more non-transitorycomputer-readable storage media of claim 12, wherein the generating thefirst list of nearby user devices is performed by one or more computingdevices of a payment processor that processes payments for multiplemerchants including the merchant.
 18. The one or more non-transitorycomputer-readable storage media of claim 12, wherein the first userdevice is a mobile device that includes a global positioning system(GPS) receiver, and the first geolocation of the first user device isdetermined based at least in part on GPS information from the GPSreceiver.
 19. The one or more non-transitory computer-readable storagemedia of claim 12, wherein the first user device is a mobile device, andthe first geolocation of the first user device is determined based atleast in part on one or more of cellphone data or wireless network data.20. The method of claim 1, further comprising receiving, by the one ormore computing devices of the payment processor, and after sending ofthe first list of nearby user devices, a request to process the cardlesspayment transaction from the first merchant device.